linting changes#1748
Merged
Merged
Conversation
Closed
RamilCDISC
approved these changes
Jun 10, 2026
RamilCDISC
left a comment
RamilCDISC
left a comment
Collaborator
There was a problem hiding this comment.
The PR adds new linting checks for non python files. The relevant files are updated to match the new linter requirements. All the changes are just formatting changes and no previous content is changed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
currently we lack json/md/yaml coverage for linter and precommit. We do run prettier after the fact but have removed it from our precommit hooks due to deprecation. This PR adds linting for the file formats that are not covered to pre-commit and resolves the call to pre-commit for all files in the readme to ensure all files in CORE are in compliance